Labels:text | font | screenshot | black and white | document OCR: NEW FEATURES OF JANUS 2. 1 BETA 2 - Improved reliability. - Improved Kickstart 2.0 compatibility. - All Amiga services are automatically loaded and run when needed. - AREAD and AWRITE support wildcards and subdirectories. Run AREAD or AWRITE with no arguments to see a list of options. - AREAD, AWRITE, JLINK, and fake PC partitions are faster. - AMOUSE3. DRV allows you to use the Amiga's mouse in Windows 3.0 {however, hardware bugs in the A2206 Bridgeboard limit windows to "real mode" only) . - AMouse on the Amiga side has become MouseServ. - PCDisk on the Amiga side has become DOSServ. BUG FIXES IN A2286 BIOS 4.2 ROMS - Printing through BIOS to the Amiga "LPT1" program should work. . You should be able to boot from certain hard drive controllers that previously couldn't (notably the Plus Hardcard II series). - No more garbage sent to printer during SHUTDOWN code (switching from protected to real mode) . - Some interrupt vectors were uninitialized. - The hard drive parameter table has been expanded. KNOWN PROBLEMS WITH JANUS 2.1 BETA 2 - Kickstart 2.0 on a CPU with a data cache: If your Amiga has a data cache (Amiga 3000, Amiga 2500, Amiga 2000 with 3rd party accelerator board) and is running Kickstart 2.0 or higher, you must disable the data cache when using the Bridgeboard. This can be accomplished by placing the command "CPU NODATACACHE" in your Startup-Sequence file "before* the "BindDrivers" command. You may also use the "Enforcer" tool, which knows about Bridgeboards and disables the data cache only for the address space occupied by the Bridgeboard. Place the command "Enforcer Quiet" in your Startup-Sequence *before" the "BindDrivers" command. You should make this modification to the s/Startup-Sequence of your 2.0 boot volume. - A2286 hardware bugs : - Programs that run in "286" or "protected" mode have trouble with the keyboard (most notably Windows 3. 0 in "standard" mode) . FIX: New B042/EPLD tower board. - Typing while Amiga <- >PC traffic is heavy (ie, AREAD or AWRITE running, JLINK' ed drive busy, fake C: drive busy) causes keys to be lost.
(.png)
